docs: Mention ignore_changes_global_secondary_index can cause table to be recreated #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mnylensc
changed the title
antonbabenko
merged commit 6f55029
into
terraform-aws-modules:master
11 of 12 checks passed
|
This PR is included in version 4.0.1 🎉 |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add a warning to the docs that setting
ignore_changes_global_secondary_indexafter table is already created will cause the table to be recreated, and provide a migration path that doesn't result in data loss, similar to how was documented for enabling autoscaling for pre-existing table.Closes #82
Motivation and Context
I feel that it's important to document cases where the resources maintained by the modules cause those resources to be recreated, as that can often come as a surprise and be only visible when reviewing the
terraform planoutput.Breaking Changes
No
How Has This Been Tested?
N/A